CustomCama

CAUTION:

When not integrated with CustomCAMA, the first five CAMA database settings must be set to INTEGRATION OFF.

For CustomCAMA Integration, the Records application setting for Cama System should be set to ProVal 7.10 or higher.

Go to Configuration > Application Settings > Maintain Applications Settings and select the setting type of Effective Date, the filter by module of Records, and click Edit on the Cama System application setting and set toProVal 7.10 or higher.  

However, if the Records Custom CAMA application settings for databases are set to INTEGRATION OFF, you will not be able to save when attempting to create a new Personal Property record, new legal party, or maintain Legal Party information. You will need to define these application settings regardless of whether your jurisdiction is integrated with CustomCAMA. When not defined, the code that keeps Aumentum and Custom CAMA in sync with one another continues to execute, which is not desirable in an environment in which Custom CAMA/ProVal are being used.

Notification is provided if Custom CAMA integrated with Aumentum is turned off. If the Records CAMA system application setting equals CustomCAMA, a call is generated to the CustomCAMA webservice or API to ensure the settings are valid. If the call fails, the alert message, Integration is not turned on. Notify your system administrator is displayed. Click OK to proceed.

NOTE: If your jurisdiction is not integrated with CustomCAMA, you must set these application settings to '[INTEGRATION OFF]'.

NOTE: Custom CAMA Integration code uses a Records API to return the subdivision code of a revenue object.

Application Settings	Date Type/ Value Type	Comment	Action
Application Setting	Date Type/Value Type	Comment	Action
CAMA ARB Database (fmt:[srv].[db].schema])	Effective Date	Enter the database name for the CAMA ARB database.	Click Edit and enter the database name. If not integrated with CustomCAMA, accept the default of [INTEGRATION OFF].
CAMA History Database (fmt:[srv].[db].[schema])	Effective Date	Enter the database name for the CAMA history database. This database stores and provides CAMA  historical data for the Aumentum/CAMA interface.	Click Edit and enter the database name. If not integrated with CustomCAMA, accept the default of [INTEGRATION OFF].
CAMA Real Estate Database (fmt:[srv].[db].[schema])	Effective Date	Enter the database name for the CAMA real estate database. This database stores and provides CAMA real estate data for the Aumentum/CAMA interface.	Click Edit and enter the database name. If not integrated with CustomCAMA, accept the default of [INTEGRATION OFF].
CAMA Tangible Asset Database (fmt:[srv].[db].[schema])	Effective Date	Enter the database name for the CAMA tangible assets database. This database stores and provides CAMA tangible asset date for the Aumentum/CAMA interface.	Click Edit and enter the database name. If not integrated with CustomCAMA, accept the default of [INTEGRATION OFF].
CAMA TIC Database (fmt:[srv].[db].[schema])	Effective Date	Enter the database name for the CAMA TIC database.	Click Edit and enter the database name. If not integrated with CustomCAMA, accept the default of [INTEGRATION OFF].
Sketch Application	Effective Date	Select the source from which a sketch is created. The default is Create sketch via Traverse.dll. The other options are Create sketch via APEX or None.	Click Edit and select the applicable sketch application source.
UNC path for Traverse DLL	Effective Date	If using Traverse.dll for the sketch application source, enter the UNC path for the Traverse DLL. NOTE: This path should be an http path, e.g., http://vsiis03/traverse/traverse.dll.	Click Edit and enter the UNC (http) path.
URL for Apex Web Service	Effective Date	Enter the database name for the Apex Web Service.	Click Edit and enter the URL path.